Use Case - Extending the data model with a new association

2 Tasks

15 mins

Pega Customer Decision Hub '24.1

Pega Customer Decision Hub '23 Pega Customer Decision Hub 8.8

Visible to: All users

Intermediate Pega Customer Decision Hub '24.1 Next Best Action English

Scenario

During the gap analysis, the project team found that the provided product holdings table did not match the requirements of U+ Comms and needed modifications. Consequently, the database team created a new table, cdhcomms_productholdings, in the ExternalMKTData database. This table contains a list of products owned by subscriptions and additional information, such as the start and end date of each product they own.

To integrate this new table with the system, build a new entity in the Customer Decision Hub and associate it with the Subscription entity in the Profile Designer.

 

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

• Log In

Detailed Tasks

1 Other details

1. The product holding database table (cdhcomms_productholdings) is created for you in the ExternalMKTData schema. As the System Architect, in Dev Studio, use the Database Class Mappings tool (Configure > Data Model > Classes & Properties > Database Class Mappings) to create the new class and associated properties for the product holdings. Use proper case notation for the properties and ensure that you create the properties in the CDH-Rules ruleset. The table includes the following details:
   1. The database table resides in the ExternalMKTData database, externalmktdata schema.
   2. The table name is cdhcomms_productholdings.
   3. Use the CDH-Rules ruleset to store the properties. Use UComms-CDH-Data-ProductHoldings as the class name for the entity.
   4. Use proper case when you create the following properties in the class:
      • HoldingID
      • HoldingName
      • StartDate
      • EndDate
      • ServiceType
      • Category
      • PurchaseChannel
      • MonthlyCost
      • SubscriptionID (Database column is SubsID)
2. In Dev Studio, create a new Database Table data set in the UComms-CDH-Data-ProductHoldings class in the CDH-Rules ruleset to access the database table, and name it Product Holdings.
   Caution: Ensure that you have the necessary keys in the Data Set to build the association. Use the following figure to ensure the correct keys are selected in the Data Set:

   

3. As the Decisioning Architect, use Profile Data Sources to add the newly created Data Set to the allow list. Then, associate the Product Holdings with the Subscription entity.

2 Acceptance criteria

1. The cdhcomms_productholdings database table is properly mapped to the UComms-CDH-Data-ProductHoldings class with the correct property names.
2. A database table Data Set, Product Holdings, is created to access the data in the database table.
3. All rules (properties, Data Set) are created in the CDH-Rules ruleset.
4. The correct Data Set keys are defined to allow the association between the product holding and the subscription entities.
5. The new Data Set is added to the allow list in Profile Data Sources and associated with the Subscription entity by using SubscriptionID in Profile Designer.

---

---

Available in the following mission:

• End-to-end Pega Customer Decision Hub Implementation v3